| 翻訳と辞書 |
| best coding practices ： ウィキペディア英語版 |
best coding practices
Best coding practices are a set of informal rules that the software development community has learned over time which can help improve the quality of software.
Many computer programs remain in use for far longer than the original authors ever envisaged (sometimes 40 years or more), so any rules need to facilitate both initial development and subsequent maintenance and enhancement by people other than the original authors.
In Ninety-ninety rule, Tim Cargill is credited with this explanation as to why programming projects often run late: "The first 90% of the code accounts for the first 10% of the development time. The remaining 10% of the code accounts for the other 90% of the development time." Any guidance which can redress this lack of foresight is worth considering.
The size of a project or program has a significant effect on error rates, programmer productivity, and the amount of management needed.
== Software quality ==
(詳細は* Is the program produced on schedule (and within budget)?
* How adaptable is the program to cope with changing requirements?
* Is the program efficient enough for the environment in which it is used?
Hoare has identified seventeen objectives related to software quality, including:
* Clear definition of purpose.
* Simplicity of use.
* Ruggedness (difficult to misuse, kind to errors).
* Early availability (delivered on time when needed).
* Reliability.
* Extensibility in the light of experience.
* Brevity.
* Efficiency (fast enough for the purpose to which it is put).
* Minimum cost to develop.
* Conformity to any relevant standards.
* Clear, accurate, and precise user documents.
抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』
■ウィキペディアで「best coding practices」の詳細全文を読む
スポンサード リンク
| 翻訳と辞書 : 翻訳のためのインターネットリソース |
Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.
|
|